First version of 18.04 upgrade documentation #60
Conversation
erelson
force-pushed
the
18.04_install
branch
from
c322616 to
8cd18f1
Compare
| .. WARNING:: | ||
| Read this document in full to ensure you understand the procedures. It is | ||
| not straightforward to go back to ROS Indigo/Ubuntu 14.04 after doing this. | ||
| Ensure your colleagues are on board with doing this upgrade. |
There was a problem hiding this comment.
I didn't check with my colleagues when I upgraded my Fetch 😆
source/indigo_to_melodic.rst
Outdated
|
|
||
| For (2), this may include workspaces, logs, and training data. | ||
|
|
||
| For (3), this file may be useful:: |
There was a problem hiding this comment.
Also if they're using any additional sensors they may have additional rules.
| #. Calibration and other robot-specific files. By convention, these are | ||
| all in ``/etc/ros/[indigo|melodic]/`` | ||
| #. Files relating to your research work | ||
| #. Network hardware configuration (for troubleshooting) |
There was a problem hiding this comment.
I'd suggest adding /opt/ros/indigo which in case anyone is relaying on some specific version of something they've installed they'd at least have a hope of getting something working again... It wouldn't be straightforward, and I wouldn't recommend it... but it might be useful.
There was a problem hiding this comment.
I'll suggest grabbing a record of what's in /opt/ros/indigo. Any suggestion on how to do that or is dpkg -l | grep ros-indigo > installed_indigo_packages.txt good enough?
There was a problem hiding this comment.
That, and simply tar the directory...
Because only the latest version is available from the package manager, so if they've installed their own packages in /opt/ros/* or happen to be depending on a very specific version which might not be available they'd have it... but of course it's not easy to get back to the state they were in so that's why I wouldn't recommend it.
There was a problem hiding this comment.
I hadn't realized how small the contents of that directory typically are. I'll make that update.
There was a problem hiding this comment.
Yeh it's basically just some binarys and header files, nothing too large.
The only thing I would hate to see is if some student who's going to be presenting a thesis soon and is off working on the writing part, then goes back to the lab after the writing is done to show it / grab a video for the defense... and the were depending on whatever version was in there.
They could flash it back to trusty/indigo and un-tar the directory, clone their workspace and no need to worry about upgrading/updating to whatever is now the latest in the indigo or melodic repos
source/indigo_to_melodic.rst
Outdated
|
|
||
| #. **Runstop the robot**, to avoid unexpected movement of the robot. | ||
| #. Download the latest 18.04 Ubuntu installer from http://releases.ubuntu.com/18.04/ | ||
| (in these instructions we use the Desktop image, version 18.04.1). Install Ubuntu |
There was a problem hiding this comment.
Just a todo for later: make instructions for the server variant of Ubuntu.
There was a problem hiding this comment.
The actual TODO is to make the installer and negate the need for these steps :) But I might take your suggestion here, and have manual steps for a server-based ubuntu setup instead of supporting an additional installer for that. (though it would potentially be super minimally different)
erelson
force-pushed
the
18.04_install
branch
from
8cd18f1 to
372d81a
Compare
erelson
force-pushed
the
18.04_install
branch
from
372d81a to
09c8733
Compare
There was a problem hiding this comment.
Overall LGTM, just a couple minor things.
But one big question...
Are the updates for "computer.rst" in another PR? There's no documentation for using systemd instead of upstart on 18.04, and there is a step to install chrony that should probably mention it is installed by default on robots bought after whatever date.
|
Good catches. I've updated the existing note about chrony (which is out of date by 2+ years). Doing a separate readthrough of the docs to attempt to cover both 14.04 and 18.04 would be a separate PR. (I suspect we'll wait til we're only shipping 18.04 research robots, and then revise the whole docs to talk about 18.04 only) |
We will officially announce when the upgrade from Indigo->Melodic is
ready. This is not yet the announcement.
Feedback on this draft is welcome, however!
See also ZebraDevs/fetch_robots#27
Also closes #47